Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Live Markdown for web refactor #394

Merged
merged 82 commits into from
Aug 21, 2024
Merged

Live Markdown for web refactor #394

merged 82 commits into from
Aug 21, 2024

Conversation

Skalakid
Copy link
Collaborator

@Skalakid Skalakid commented Jun 20, 2024

Details

This PR refactors the web implementation of the Live Markdown library. The main goals of it are:

  • enhancing algorithms and logic behind Markdown Input, to make the project more flexible and enable the possibility of adding new more complex features like inline images or code blocks
  • changing and organizing Markdown input HTML structure, to meet the industry standards, fixing problems with cursor positioning and problems with scrolling into view
  • improving code quality, to make the codebase more understandable and boost the developer experience

During this refactor phase we:

  • changed web live markdown HTML structure so now:

    • every line is represented as paragraph element <p> - it makes structure much clear and organized, and enables us to apply custom logic to specific lines
    • every text is wrapped with <span data-type="text"> tag - by wrapping text with HTML element we enable many useful functions that aren't available in normal text node, for example: scrollIntoView()
    • instead of \n characters inside the input's HTML structure we use <br> tags - br tags give use much more flexibility and fix problem with cursor navigation when using arrow keys when moving between markdown components
    • every <br> tag is wrapped with <span data-type="br"> tag - it fixes many problems connected to cursor positioning

    Thanks to the new structure we enabled the usage of many styles that were generating a lot of bugs in the past, like display: block. Also were able to remove all workarounds connected to cursor positioning.

  • added HTML tree node structure, that represents current HTML dom and stores many important information about every element inside the input. Thanks to this tree structure we can easily interact with the markdown elements and we were able to completely refactor and improve the performance of cursor positioning algorithms

  • replaced all text value representation functions like process value or normalizeValue with one textContent variable that always contains properly formatted text value without any additional newlines from contentEditable

  • split long files of code into smaller ones, and sort functions into utils

  • prepared the code for new, more complex features like inline images

This refactor was made as a part of inline image feature. After discovering some structure and logic limitations when creating inline image POC we decided to improve Live Markdown for web.

This refactor will fix or unblock following issues:

Related Issues

GH_LINK

Manual Tests

Since it's a big change it would be great to test it in all cases connected to:

  1. Adding text / Markdown
  2. Selection
  3. Cursor positioning
  4. Number of lines
  5. Scroll into view
  6. Placeholder
  7. History - undo/redo
  8. Pasting
  9. Copy / Cut
  10. Composition events
    • Web:
      • Diacritics
      • Text replacement on mac
    • mWeb:
      • Diacritics
      • Autocorrection
  11. Spellcheck
    • Web:
      • Chrome
      • Safari
      • Firefox (not working)
    • mWeb:
      • iOS Safari
      • Android Chrome

Linked PRs

Expensify/App#40181 (comment)

@Skalakid Skalakid changed the title @skalakid/web parser refactor Live Markdown for web refactor Jun 20, 2024
@Skalakid Skalakid force-pushed the @Skalakid/web-parser-refactor branch from 701962c to 38693c4 Compare June 26, 2024 13:58
@Skalakid Skalakid requested a review from tomekzaw June 28, 2024 16:22
@Skalakid Skalakid self-assigned this Jun 28, 2024
@Skalakid Skalakid added enhancement New feature or request labels Jun 28, 2024
@JKobrynski
Copy link

JKobrynski commented Jul 31, 2024

I've been trying to fix this Android web issue (you can see some of my takeaways in the comments). It led me to parseText method in parserUtils.ts, more specifically these lines:

 if (!rootSpan || rootSpan.innerHTML !== dom.innerHTML) {
      targetElement.innerHTML = '';
      targetElement.innerText = '';
      target.appendChild(dom);

      if (BrowserUtils.isChromium) {
        moveCursor(isFocused, alwaysMoveCursorToTheEnd, cursorPosition, target);
      }
 }

I also contacted @BartoszGrajdek (shout out to him) to discuss it and he suggested to give this PR a try, as it refactors the web implementation. Here is what I discovered on both web and Android web:

(I had to remove TEST_CONST.EXAMPLE_CONTENT as the bug that I'm trying to fix only occurs for an empty input)

Case 1

- const [value, setValue] = React.useState(TEST_CONST.EXAMPLE_CONTENT);
+ const [value, setValue] = React.useState();

Voice recognition works, markdown doesn't work

Case 2

- const [value, setValue] = React.useState(TEST_CONST.EXAMPLE_CONTENT);
+ const [value, setValue] = React.useState('');

Voice recognition doesn't work, markdown works

To test the voice recognition, I started from an empty input and dictated a sentence, to test markdown I simply typed * bold * or something similar.

@Skalakid Skalakid force-pushed the @Skalakid/web-parser-refactor branch from b5e9b86 to 4e895e9 Compare August 20, 2024 09:07
BartoszGrajdek
BartoszGrajdek previously approved these changes Aug 20, 2024
Copy link
Collaborator

@BartoszGrajdek BartoszGrajdek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! ✅

@Skalakid Skalakid merged commit 1be6561 into main Aug 21, 2024
5 checks passed
@Skalakid Skalakid deleted the @Skalakid/web-parser-refactor branch August 21, 2024 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants